Microsoft Dynamics eConnect Integration

The NetForum integration for Great Plains eConnect requires the use of the eConnect along with Microsoft Dynamics (formerly Great Plains) to assist customers with importing batch data to Dynamics. The eConnect integration, unlike the other accounting integrations, uses XML to transfer the data. Contact Microsoft support or a 3rd party consultant for more details on how to use eConnect. Abila does not support "how to?" questions related to 3rd party software such as Microsoft Dynamics, which must be licensed separately from the 3rd party vendor by the customer.

This integration is available with NetForum 2.0 Service Pack 5.

To take advantage of this integration, you will need eConnect as well as the Great Plains 10 Web Service Application installed. This web service sites on top of eConnect and is what the integration interacts with.

To take advantage of this integration, you will need eConnect as well as the Great Plains 10 Web Service Application installed. This web service sites on top of eConnect and is what the integration interacts with.

Important! This integration has been tested only with GP 10.0 with runtime version of eConnect

There are two current bugs on the Great Plains side that we had to work around:

  • Inability to Auto-Number JournalId — JournalId is an incrementing number that is not managed in NetForum but is required by GP. eConnect can auto-number the JournalId but the GP Web Service is not currently capable of taking advantage of this eConnect feature (I can forward a thread from Microsoft support if anyone is interested). The workaround is to retrieve the next JournalId through the Great Plains transaction import "pre-processing" stored procedure and pass it along to the main transaction processing SP (œbefore save extension in NetForum). I will provide the code snip required to implement this. Typically, this might be done by the customer's GP consultant but they didn't know how to do it so we had to figure it out
  • Great Plains Web Service crashes (worker process issue!) when trying to import G/L Transactions if the GP Multi-Currency feature is disabled. You don't have to setup any currencies other than USD, but you need to enable the feature in GP.

There are bug reports open with Microsoft related to these two issues.

Important! Client needs to contact Abila for this integration prior to its use.

Setting Up Microsoft Dynamics eConnect

Client Tasks

  • Client is responsible in installing Dynamics GP 10.0 with runtime version of eConnect
  • Client need to provide all eConnect configuration information to Abila
  • Client needs to have knowledge about GP eConnect
  • Client is highly recommended to have a consultant for GP eConnect
  • Client is responsible for any eConnect changes such as new features, bug fixes and changes
  • Client understands that Abila will only configure the integration specified in this document and Abila is not responsible for configuration or any changes in eConnect
  • Client needs to perform all testing for batch posting and verify accuracy of information in eConnect
  • Client understands additional fee will incur if any changes to eConnect (Service Pack or new Release) causes the integration to break

Abila Tasks

  • Abila will set up the configuration file
  • Abila will set up the system option
  • Abila will work with the client to obtain the information from eConnect for the configuration

Costs

To configure Microsft Dynamics eConnect in NetForum, please contact Abila for pricing. The cost to implement this interface will require an initial setup fee and a monthly fee

Usage and Instructions

The BatchExportFormat system option needs to be set to eConnect.

There is a .config file for the integration that needs to be configured. The settings that need configuration are:

  • DynamicsGPWebService_DynamicsGP_Dynamics_x0020_CompanyId
    • This stores the translation from the Company Codes in NetForum to the Company IDs in Dynamics. For multiple companies, the values can be set up as NFCode:DynID;NFCode2:DynID2. An example with real companies may look like AV:1;AVF:2
  • DynamicsGPWebService_DynamicsGP_Dynamics_x0020_GP
    • This is the location of the eConnect web service.
  • DynamicsGPWebService_DynamicsGP_Dynamics_x0020_Login
    • This stores the login name for eConnect
  • DynamicsGPWebService_DynamicsGP_Dynamics_x0020_Pwd
    • The password for connecting to eConnect is stored here
  • DynamicsGPWebService_DynamicsGP_Dynamics_x0020_Domain
    • This is the domain for the login being used.

Tip: This process requires that you modify the BatchExportFormat system option.